Skip to content

Integrate FFmpeg development checker and failure-stage feedback - #2

Open
loopx-agent wants to merge 2 commits into
codex/ffmpeg-feedback-boundary-20261107from
codex/ffmpeg-feedback-dev-integration-20261107
Open

loopx-agent wants to merge 2 commits into
codex/ffmpeg-feedback-boundary-20261107from
codex/ffmpeg-feedback-dev-integration-20261107

Conversation

@loopx-agent

@loopx-agent loopx-agent commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

This task-source integration combines upstream EdgeBench PR ByteDance-Seed#58’s bounded verifier-stage feedback with PR ByteDance-Seed#59’s public scalar-reference correctness checker. Both proposed task changes independently used version 1.0.1; this branch retains the feedback as 1.0.1 and records the checker addition as 1.0.2 in one Changes section.

The two reviewed heads are merge ancestors. The public checker and both instruction files are byte-identical to PR ByteDance-Seed#59. Every judge file is byte-identical to PR ByteDance-Seed#58; task metadata differs from PR ByteDance-Seed#58 only in version. No scoring thresholds, workloads, rescale, validity or limits change in this composition.

Validation: full repository suite 44 passed, 1 skipped; targeted source comparisons and public-boundary checks pass. The skip is the optional E2B provider module, whose dependency is not installed. A separately tagged compatibility work image was built from the previously validated legacy work image, changing only the checker and local instruction copies at both existing workspace paths. Installed non-root, network-disabled qualification passed the real public CLI against the scalar reference (13/13) and rejected an invalid ABI fixture (0/13, exit 1). The judge image identity is unchanged. This is compatibility-image qualification, not a migration to the current upstream runtime; no active image tag or experiment was modified, and no model or score-benefit claim is made.

This PR intentionally targets the task-source feedback branch in the fork. It does not replace the independently pinned operational SForge provider with current upstream APIs, nor merge either upstream PR into upstream main.

Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants